Conversation
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
d9def93 to
4f29cbe
Compare
This comment has been minimized.
This comment has been minimized.
014d61d to
6b45680
Compare
|
I don't think jieyouxu will want to review this part of rustc. |
|
|
This comment has been minimized.
This comment has been minimized.
6b45680 to
1c28bd8
Compare
This comment has been minimized.
This comment has been minimized.
c310bf7 to
b2b51e4
Compare
|
@rustbot reroll |
b2b51e4 to
3fb0092
Compare
3fb0092 to
446bd1d
Compare
This comment has been minimized.
This comment has been minimized.
|
spurious failure, cc @jieyouxu |
|
There's an issue at #93784. |
This comment has been minimized.
This comment has been minimized.
446bd1d to
d8a440f
Compare
This comment has been minimized.
This comment has been minimized.
d8a440f to
544a019
Compare
|
This PR was rebased onto a different main commit. Here's a range-diff highlighting what actually changed. Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers. |
|
The individual commits seem like they don't have a reason to be separate, so please squash them. |
544a019 to
b28b622
Compare
|
One of the commits had gotten lost over one of the last rebases. I've re-added it and fused them. |
|
r=me, just one question about the |
…t_all_rtls into global ctor
b28b622 to
6de0591
Compare
|
@bors r=nnethercote rollup |
…thercote Cleanup offload datatransfer There are 3 steps to run code on a GPU: Copy data from the host to the device, launch the kernel, and move it back. At the moment, we have a single variable describing the memory handling to do in each step, but that makes it hard for LLVM's opt pass to understand what's going on. We therefore split it into three variables, each only including the bits relevant for the corresponding stage. cc @jdoerfert @kevinsala r? compiler
There are 3 steps to run code on a GPU: Copy data from the host to the device, launch the kernel, and move it back.
At the moment, we have a single variable describing the memory handling to do in each step, but that makes it hard for LLVM's opt pass to understand what's going on. We therefore split it into three variables, each only including the bits relevant for the corresponding stage.
cc @jdoerfert @kevinsala
r? compiler